Add optional depth parameter to SDK file listing methods. #649
Conversation
* update js-sdk file.list method to include optional depth param * update js-sdk tests
|
|
Also, add docstrings for the new I'll document the spec update process so it is not blocking. |
|
This is blocked by the unpredictable Python client generation, right? |
@ValentaTomas yes, per discussion, im on a side-quest to build a predictable codegen, will apply it here and commit. |
* create codegen script using this container with mapped volumes * adapt Makefiles to this new approach * adapt where we install the connect-python protobuf binary for this to work
…e-files-list-in-the-sdk-e2b-1902_2
…rsive-files-list-in-the-sdk-e2b-1902_2
…files-list-in-the-sdk-e2b-1902_2
mishushakov
left a comment
There was a problem hiding this comment.
Looks fine, the only things I am questioning if we should hardcode the default depth (any other examples where we hardcode a parameter like this?) and if we can reduce some repetition in the tests (using loops?)
…files-list-in-the-sdk-e2b-1902_2
…files-list-in-the-sdk-e2b-1902_2
`npx changeset` for the release of #649
Description
Do not merge before e2b-dev/infra#524 is merged and deployed.
The DX would look like this:
envdpb specjs-sdkjs-sdkfile.listmethod to include optional depth paramjs-sdktestspython-sdkpython-sdkfile.listmethod to include optional depth parampython-sdktests